Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30]) by watsun.cc.columbia.edu (8.8.3/8.8.3) with ESMTP id LAA21108 for <kermit.misc@watsun.cc.columbia.edu>; Mon, 9 Dec 1996 11:30:34 -0500 (EST)
Received: (from news@localhost) by newsmaster.cc.columbia.edu (8.8.3/8.8.3) id LAA24720 for kermit.misc@watsun; Mon, 9 Dec 1996 11:30:33 -0500 (EST)
Path: news.columbia.edu!not-for-mail
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: dialing macro for dialback modem
Date: 9 Dec 1996 11:30:21 -0500
Organization: Columbia University
Lines: 17
Message-ID: <58heqt$kcd@watsun.cc.columbia.edu>
References: <32A88B82.41C67EA6@panix.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
In article <32A88B82.41C67EA6@panix.com>,
Kurt Rosenhagen <kjr@panix.com> wrote:
: Ive modified an existing macro for dialing in to a dialback modem. When
: the dialback occurs, an "INPUT" command is executed, and the message
: "Cant condition line for input" appears five times (there are siz input
: commands after dialback). The message "Connecting to cua0" etc apperas,
: script file is finished as kermit now expects input from keyboaard.
:
So this means you are probably using C-Kermit? Which version?
On which platform?
Anyway, the trick of handling dialback situations is that you
have to hang up the modem after making the call, so it can call
you back. If you don't hang it up, it will just get a busy